docs: sync README and runbook with 0.3.0 and 0.3.1 - #32
Merged
Conversation
- README alerting list: cardinality ceiling is 30k, add the spike and uncovered-project rules - README hooks row: infra-validate runs at push when infra/ changed - Runbook: document cutting a release, which lived only in a workflow comment
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The 0.3.1 changelog moved the cardinality ceiling and added a spike rule, but
the README's alerting section still described the old thresholds. The release
procedure introduced in 0.3.1 lived only in a comment at the top of
release.yml, where no operator reads it.PrometheusCardinalitySpikeandProjectsUncovered, which were missing.just hooksalso installsinfra-validateat pushwhen
infra/changed.section, tag and push, then re-bootstrap each spoke at the new tag.
Docs only. No config or code touched.